ERROR [SetCurrentIdentityFilter] Not found identity in IdentityRegistry for user root, check Login Module.
For performance reasons, part of the Javascript and CSS have changed. With 5.2 only some levels of navigation nodes are loaded and the others are loaded on demand, also the markup produced by the portal has been drastically simplified. Simplifying the markup helped a lot decreasing the size of what transits over the network but also speed up its rendering on web browsers.
This has not been changed and, while performing the migration, your web browser may still have the content of previous portal in cache. You will need to empty your web browser cache if you see that the UI is malformed or if overlay menus are not appearing. With most browsers you can refresh the cache by clicking on Ctrl+F5 while being on the problematic page.
On some rare occasions after using JBoss Enterprise Portal Platform 5.1 and 5.2 alternatively during migration phase, the portal may not answer and, during login, errors such as the following may appear:
11:33:07,011 ERROR [GTNPORTAL:SetCurrentIdentityFilter] Not found identity in IdentityRegistry for user root, check Login Module.
ERROR [SetCurrentIdentityFilter] Not found identity in IdentityRegistry for user root, check Login Module.
May appear.
To solve this issue, delete your cookies for the domain or localhost.